ASP.NET Configuration

My solution was to turn off customErrors and implement it at a lower level as described by this article that the stack overflow post links.

Create a <customErrors> tag within a web.config configuration file located in the root directory of the current web application.

I recommend following the instructions provided in the error message to disable the customErrors mode and view the actual error. Additionally, ...

當使用者在ASP.NET Web 應用程式中發生執行階段錯誤時，會看到什麼？ 答案取決於網站的< customErrors > 設定方式。 根據預設，使用者會顯示不明顯黃色的 ...

Have you checked the customErrors mode in directories above your application or the machine.config? It's possible that one of these config ...

Searching around I found that perhaps it might be because the app pool identity was set on site folder permission and indeed it wasn't, so I set ...

An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being ...

Your problem is you are catching the error and then redirecting to the error page, so there is no unhandled error -- meaning no error is ...

customErrors mode is meant for debugging purposes and won't work once deployed to the server unless you set compilation debug=true.

I have set customError mode off in my web config and I'm getting an error code of The 'mode' attribute is invalid ' The value 'off' is invalid according to ...